Resource reservation

ABSTRACT

Apparatuses, methods, and systems are disclosed for resource reservation. One apparatus ( 200 ) includes a receiver ( 212 ) that receives ( 802 ) an indication of resource reservation for uplink communication. The indication is based on information reported from a first remote unit. The apparatus ( 200 ) also includes a processor ( 202 ) that determines ( 804 ) a resource based on the indication. The apparatus ( 200 ) includes a transmitter ( 210 ) that transmits ( 806 ) data on the resource.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to resource reservation.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Positive-Acknowledgment (“ACK”), BinaryPhase Shift Keying (“BPSK”), Clear Channel Assessment (“CCA”), CyclicPrefix (“CP”), Channel State Information (“CSI”), Common Search Space(“CSS”), Discrete Fourier Transform Spread (“DFTS”), Downlink ControlInformation (“DCI”), Downlink (“DL”), Downlink Pilot Time Slot(“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced MobileBroadband (“eMBB”), Evolved Node B (“eNB”), European TelecommunicationsStandards Institute (“ETSI”), Frame Based Equipment (“FBE”), FrequencyDivision Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”),Guard Period (“GP”), Hybrid Automatic Repeat Request (“HARQ”),Internet-of-Things (“IoT”), Licensed Assisted Access (“LAA”), Load BasedEquipment (“LBE”), Listen-Before-Talk (“LBT”), Long Term Evolution(“LTE”), Multiple Access (“MA”), Modulation Coding Scheme (“MCS”),Machine Type Communication (“MTC”), Multiple Input Multiple Output(“MIMO”), Multi User Shared Access (“MUSA”), Narrowband (“NB”),Negative-Acknowledgment (“NACK”) or (“NAK”), Next Generation Node B(“gNB”), Non-Orthogonal Multiple Access (“NOMA”), Orthogonal FrequencyDivision Multiplexing (“OFDM”), Primary Cell (“PCell”), PhysicalBroadcast Channel (“PBCH”), Physical Downlink Control Channel (“PDCCH”),Physical Downlink Shared Channel (“PDSCH”), Pattern Division MultipleAccess (“PDMA”), Physical Hybrid ARQ Indicator Channel (“PHICH”),Physical Random Access Channel (“PRACH”), Physical Resource Block(“PRB”), Physical Uplink Control Channel (“PUCCH”), Physical UplinkShared Channel (“PUSCH”), Quality of Service (“QoS”), Quadrature PhaseShift Keying (“QPSK”), Radio Resource Control (“RRC”), Random AccessProcedure (“RACH”), Random Access Response (“RAR”), Reference Signal(“RS”), Resource Spread Multiple Access (“RSMA”), Round Trip Time(“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”),Scheduling Request (“SR”), Single Carrier Frequency Division MultipleAccess (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel (“SCH”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), System InformationBlock (“SIB”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink ControlInformation (“UCI”), User Entity/Equipment (Mobile Terminal) (“UE”),Uplink (“UL”), Universal Mobile Telecommunications System (“UMTS”),Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability and Low-latencyCommunications (“URLLC”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”). As used herein, “HARQ-ACK” may represent collectivelythe Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NAK”).ACK means that a TB is correctly received while NAK means a TB iserroneously received.

In certain wireless communications networks, URLLC may have a datapayload that is small. According to some configurations, URLLC may havea periodically occurring packet arrival rate and a packet size may be 32bytes, 50 bytes, 200 bytes, and so forth.

In certain configurations, for URLLC, the user plane latency may be 0.5ms for UL, and 0.5 ms for DL. In various configurations, for eMBB, theuser plane latency may be 0.4 ms for UL and DL. Moreover, URLLCreliability may be evaluated by a success probability of transmitting Xbytes within 1 ms. This may be the time it takes to deliver a small datapacket from the radio protocol layer 2/3 service data unit (“SDU”)ingress point to the radio protocol layer 2/3 SDU egress point of theradio interface, at a certain channel quality (e.g., coverage-edge). Invarious configurations, the target for reliability may be 1-10⁻⁵ within1 ms. In certain configurations, a general URLLC reliability requirementfor one transmission of a packet may be 1-10-5 for X bytes (e.g., 20bytes) with a user plane latency of 1 ms.

In some configurations, URLLC and eMBB services may be multiplexed in asame carrier. Data collisions may occur in configurations in which URLLCand eMBB are multiplexed.

BRIEF SUMMARY

Apparatuses for resource reservation are disclosed. Methods and systemsalso perform the functions of the apparatus. In one embodiment, theapparatus includes a receiver that receives an indication of resourcereservation for uplink communication. In various embodiments, theindication is based on information reported from a first remote unit.The apparatus also includes a processor that determines a resource basedon the indication. In certain embodiments, the apparatus includes atransmitter that transmits data on the resource.

In one embodiment, the receiver receives the indication of resourcereservation for uplink communication in downlink control information. Ina further embodiment, the indication includes a single bit indicatingwhether an uplink communication resource pattern is used. In certainembodiments, the receiver receives information indicating the uplinkcommunication resource pattern. In some embodiments, the uplinkcommunication resource pattern is predefined or preconfigured.

In various embodiments, the indication includes multiple bits indicatinga selected uplink communication resource pattern of multiple uplinkcommunication resource patterns. In some embodiments, the processoridentifies the selected uplink communication resource pattern of themultiple uplink communication resource patterns using the indication.

A method for resource reservation, in one embodiment, includes receivingan indication of resource reservation for uplink communication. Incertain embodiments, the indication is based on information reportedfrom a first remote unit. The method also includes determining aresource based on the indication. The method includes transmitting dataon the resource.

In one embodiment, an apparatus includes a receiver that receivesinformation from a first remote unit. In various embodiments, theinformation includes a traffic type, a traffic period, a payload size, adelay tolerance, or some combination thereof. In certain embodiments,the apparatus includes a processor that generates an indication ofresource reservation for uplink communication based on the information.In some embodiments, the apparatus includes a transmitter that transmitsthe indication of resource reservation for uplink communication tobroadband second remote unit.

In one embodiment, the transmitter transmits the indication of resourcereservation for uplink communication in downlink control information. Ina further embodiment, the indication includes a single bit indicatingwhether an uplink communication resource pattern is used. In certainembodiments, the transmitter transmits information indicating the uplinkcommunication resource pattern. In some embodiments, the uplinkcommunication resource pattern is predefined or preconfigured. Invarious embodiments, the indication includes multiple bits indicating aselected uplink communication resource pattern of multiple uplinkcommunication resource patterns.

A method for resource reservation, in one embodiment, includes receivinginformation from a first remote unit. In certain embodiments, theinformation includes a traffic type, a traffic period, a payload size, adelay tolerance, or some combination thereof. The method also includesgenerating an indication of resource reservation for uplinkcommunication based on the information. The method includes transmittingthe indication of resource reservation for uplink communication tobroadband second remote unit.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for dynamic resource reservation;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for dynamic resource reservation;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for dynamic resource reservation;

FIG. 4 illustrates one embodiment of communications for dynamic resourcereservation;

FIG. 5 is a schematic block diagram illustrating one embodiment ofcommunications for dynamic resource reservation;

FIG. 6 is a schematic block diagram illustrating another embodiment ofcommunications for dynamic resource reservation;

FIG. 7 is a schematic block diagram illustrating a further embodiment ofcommunications for dynamic resource reservation;

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method for dynamic resource reservation; and

FIG. 9 is a schematic flow chart diagram illustrating another embodimentof a method for dynamic resource reservation.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. These code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 fordynamic resource reservation. As used herein, the term “dynamic” maymean changeable as desired during operation. For example, a “dynamicresource reservation” may be a resource reservation that may changeduring operation based on one or more resources to be reserved. In oneembodiment, the wireless communication system 100 includes remote units102 and base units 104. Even though a specific number of remote units102 and base units 104 are depicted in FIG. 1, one of skill in the artwill recognize that any number of remote units 102 and base units 104may be included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 102 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 102 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 102may communicate directly with one or more of the base units 104 via ULcommunication signals.

The base units 104 may be distributed over a geographic region. Incertain embodiments, a base unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, or by any otherterminology used in the art. The base units 104 are generally part of aradio access network that includes one or more controllers communicablycoupled to one or more corresponding base units 104. The radio accessnetwork is generally communicably coupled to one or more core networks,which may be coupled to other networks, like the Internet and publicswitched telephone networks, among other networks. These and otherelements of radio access and core networks are not illustrated but arewell known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with the LTE of the 3GPP protocol, wherein the base unit 104transmits using an OFDM modulation scheme on the DL and the remote units102 transmit on the UL using a SC-FDMA scheme or an OFDM scheme. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication protocol, for example,WiMAX, among other protocols. The present disclosure is not intended tobe limited to the implementation of any particular wirelesscommunication system architecture or protocol.

The base units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 104 transmit DL communication signalsto serve the remote units 102 in the time, frequency, and/or spatialdomain.

In one embodiment, a base unit 104 may receive information from anultra-reliable and low latency communication remote unit. Theinformation may include a traffic type, a traffic period, a payloadsize, a delay tolerance, or some combination thereof. In someembodiments, the base unit 104 may generate an indication of dynamicresource reservation for ultra-reliable and low latency communicationbased on the information. In various embodiments, the base unit 104 maytransmit the indication of dynamic resource reservation forultra-reliable and low latency communication to an enhanced mobilebroadband remote unit. Accordingly, a base unit 104 may be used fordynamic resource reservation.

In another embodiment, a remote unit 102 may receive an indication ofdynamic resource reservation for ultra-reliable and low latencycommunication. The indication may be based on information reported froman ultra-reliable and low latency communication remote unit. The remoteunit 102 may determine a resource based on the indication. The remoteunit 102 may transmit data on the resource. Accordingly, a remote unit102 may be used for dynamic resource reservation.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used fordynamic resource reservation. The apparatus 200 includes one embodimentof the remote unit 102. Furthermore, the remote unit 102 may include aprocessor 202, a memory 204, an input device 206, a display 208, atransmitter 210, and a receiver 212. In some embodiments, the inputdevice 206 and the display 208 are combined into a single device, suchas a touchscreen. In certain embodiments, the remote unit 102 may notinclude any input device 206 and/or display 208. In various embodiments,the remote unit 102 may include one or more of the processor 202, thememory 204, the transmitter 210, and the receiver 212, and may notinclude the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Incertain embodiments, the processor 202 may determine a resource based onan indication. The processor 202 is communicatively coupled to thememory 204, the input device 206, the display 208, the transmitter 210,and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 stores data relating to resources. In some embodiments,the memory 204 also stores program code and related data, such as anoperating system or other controller algorithms operating on the remoteunit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thebase unit 104 and the receiver 212 is used to receive DL communicationsignals from the base unit 104. In one embodiment, the receiver 212 maybe used to receive an indication of dynamic resource reservation forultra-reliable and low latency communication. The indication may bebased on information reported from an ultra-reliable and low latencycommunication remote unit. In certain embodiments, the transmitter 210may be used to transmit data on a resource determined based on theindication. Although only one transmitter 210 and one receiver 212 areillustrated, the remote unit 102 may have any suitable number oftransmitters 210 and receivers 212. The transmitter 210 and the receiver212 may be any suitable type of transmitters and receivers. In oneembodiment, the transmitter 210 and the receiver 212 may be part of atransceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used fordynamic resource reservation. The apparatus 300 includes one embodimentof the base unit 104. Furthermore, the base unit 104 may include aprocessor 302, a memory 304, an input device 306, a display 308, atransmitter 310, and a receiver 312. As may be appreciated, theprocessor 302, the memory 304, the input device 306, the display 308,the transmitter 310, and the receiver 312 may be substantially similarto the processor 202, the memory 204, the input device 206, the display208, the transmitter 210, and the receiver 212 of the remote unit 102,respectively.

In some embodiments, the receiver 312 is used to receive informationfrom an ultra-reliable and low latency communication remote unit (e.g.,a remote unit that communicates via URLLC). In such embodiments, theinformation may include a traffic type, a traffic period, a payloadsize, a delay tolerance, or some combination thereof. In certainembodiments, the processor 302 may generate an indication of dynamicresource reservation for ultra-reliable and low latency communicationbased on the information. In various embodiment, the transmitter 310 isused to transmit the indication of dynamic resource reservation forultra-reliable and low latency communication to an enhanced mobilebroadband remote unit (e.g., a remote unit that communicates via eMBB).Although only one transmitter 310 and one receiver 312 are illustrated,the base unit 104 may have any suitable number of transmitters 310 andreceivers 312. The transmitter 310 and the receiver 312 may be anysuitable type of transmitters and receivers. In one embodiment, thetransmitter 310 and the receiver 312 may be part of a transceiver.

FIG. 4 illustrates one embodiment of communications 400 for dynamicresource reservation. Specifically, communications 400 between a firstUE 402, a second UE 404, and a gNB 406 are illustrated. The first UE 402may be a URLLC UE (e.g., an URLLC remote unit 102) and the second UE 404may be an eMBB UE (e.g., an eMBB remote unit 102). The communications400 may facilitate dynamic resource reservation for multiplexing eMBBand URLLC.

A first communication 408 may include a message sent from the first UE402 to the gNB 406 including information, such as a traffic type, atraffic period, a payload size, a delay tolerance, or some combinationthereof. The gNB 406 may generate an indication of dynamic resourcereservation for URLLC based on the information.

A second communication 410 may include a message sent from the gNB 406to the second UE 404 including the indication of dynamic resourcereservation for URLLC. In certain embodiments, the second communication410 may include eMBB control information having the indication. Thedynamic indicator may, in some embodiments, indicate a resourcereservation of resources to be used by URLLC. The second UE 404 may beable to determine the resources to be used by URLLC by decoding its owneMBB control information. The dynamic indicator may be single bit ormultiple bits indicating a reservation pattern. In certain embodiments,the second communication 410 may include an UL-grant including anindicator of resource reservation to inform the second UE 404 topuncture the transmission and/or transmit with less power (e.g.,including down to zero) in an overlapped resource portion (e.g.,subslots) to facilitate URLLC UL transmission. In some embodiments, thesecond communication 410 may include an indicator to inform the secondUE 404 to perform rate matching via a predefined or preconfiguredresource pattern. In various embodiments, the second communication 410may include a resource reservation pattern for both DL and UL. Theresource reservation pattern for DL and UL may, in certain embodiments,include an UL resource pattern that may cover all symbols of one TTI foreMBB and for DL may avoid overlapping with a DL and/or UL control part.

The second UE 404 may determine a resource based on the indication. Forexample, the second UE 404 may determine whether resources for its owneMBB communication overlap with URLLC communication of the first UE 402,and may adjust timing of eMBB communication accordingly (e.g., determinethe resource for eMBB communication). A third communication 412 mayinclude data transmitted from the second UE 404 to the gNB 406 on theresource.

FIG. 5 is a schematic block diagram illustrating one embodiment ofcommunications 500 for dynamic resource reservation. The communications500 include a first subframe 502 and a second subframe 504. Moreover,the first subframe 502 includes a first eMBB DL control information 506,and the second subframe 504 includes a second eMBB DL controlinformation 508. Further, the first subframe 502 includes a firstpossible URLLC resource 510, a second possible URLLC resource 512, athird possible URLLC resource 514, and a fourth possible URLLC resource516. The second subframe 504 includes a fifth possible URLLC resource518, a sixth possible URLLC resource 520, a seventh possible URLLCresource 522, and an eighth possible URLLC resource 524. The first eMBBDL control information 506 and/or the second eMBB DL control information508 may include one or more indicators used to indicate URLLCcommunication to an eMBB UE.

In some embodiments, the one or more indicators may include a 1 bitindicator that represent whether a URLLC transmission resource patternis used. The URLLC transmission resource pattern may be predefined orpreconfigured for a gNB and an eMBB UE. In one embodiment, thetransmission resource pattern may be “1111” to indicate that allpossible URLLC resources in a subframe are used. For example, as shownin FIG. 5, if a URLLC resource is used for transmission, the indicatorin the first eMBB DL control information 506 may be set to “1” and theindicator in the second eMBB DL control information 508 may be set to“0.” Accordingly, the DL or UL eMBB data transmission will not occupyURLLC resources (e.g., the shaded URLLC possible resources—the firstpossible URLLC resource 510, the second possible URLLC resource 512, thethird possible URLLC resource 514, and the fourth possible URLLCresource 516) for eMBB data transmission. In contrast, eMBB datatransmission will occupy unused URLLC resources (e.g., the unshadedURLLC possible resources—the fifth possible URLLC resource 518, thesixth possible URLLC resource 520, the seventh possible URLLC resource522, and the eighth possible URLLC resource 524). The transmissionresource pattern may be used to indicate two subslots in one eMBBsubframe or four subsolts in one eMBB subframe based on a period ofURLLC packet generation and transmission, transmission granularity inone subframe, a number of retransmissions, and so forth. The predefinedor preconfigured transmission resource pattern facilitates a tradeoffbetween signaling overhead and scheduling flexibility.

FIG. 6 is a schematic block diagram illustrating another embodiment ofcommunications 600 for dynamic resource reservation. The communications600 include a first subframe 602 and a second subframe 604. Moreover,the first subframe 602 includes a first eMBB DL control information 606,and the second subframe 604 includes a second eMBB DL controlinformation 608. Further, the first subframe 602 includes a firstpossible URLLC resource 610, a second possible URLLC resource 612, athird possible URLLC resource 614, and a fourth possible URLLC resource616. The second subframe 604 includes a fifth possible URLLC resource618, a sixth possible URLLC resource 620, a seventh possible URLLCresource 622, and an eighth possible URLLC resource 624. The first eMBBDL control information 606 and/or the second eMBB DL control information608 may include one or more indicators used to indicate URLLCcommunication to an eMBB UE.

In various embodiments, the one or more indicators may include multiplebits that correspond to a URLLC transmission pattern and indicatewhether possible URLLC resources are used (e.g., in bitmap manner). Forexample, as shown in FIG. 6, 4 bits indicate 4 possible URLLCtransmission subslots in bitmap manner. Specifically, as illustrated,the indicator in the first eMBB DL control information 606 may be set to“0111” and the indicator in the second eMBB DL control information 608may be set to “1100.” Accordingly, the DL or UL eMBB data transmissionwill not occupy corresponding URLLC resources in the first subframe 602(e.g., the shaded URLLC possible resources—the second possible URLLCresource 612, the third possible URLLC resource 614, and the fourthpossible URLLC resource 616) for eMBB data transmission. In addition,the DL or UL eMBB data transmission will not occupy corresponding URLLCresources in the second subframe 604 (e.g., the shaded URLLC possibleresources—the fifth possible URLLC resource 618 and the sixth possibleURLLC resource 620). In other embodiments, if the URLLC only transmitsin the first and the third subslots, and the second and fourth subslotsmay be used by eMBB DL/UL transmission, the indicator in the eMBBcontrol information may be set to “1010.” In certain embodiments, if theURLLC only transmits in the first three subslots in one subframe, theindicator may be set to “1110.” This indication method takes more bitsin eMBB control information than the one bit indication, but is able toindicate URLLC transmission subslots more accurately. Moreover, thismultiple bit indication may reduce unnecessary waste of resources andimprove the spectrum efficiency of eMBB transmissions. The number ofindication bits in eMBB control information may be defined based on apayload size of eMBB control information, a period of URLLC packetgeneration and transmission, transmission granularity in one subframe,available bandwidth in a frequency domain, a number of retransmission,and so forth.

FIG. 7 is a schematic block diagram illustrating a further embodiment ofcommunications 700 for dynamic resource reservation. The communications700 include a first subframe 702 and a second subframe 704. Moreover,the first subframe 702 includes a first eMBB DL control information 706,and the second subframe 704 includes a second eMBB DL controlinformation 708. Further, the first subframe 702 includes a firstpossible URLLC resource 710, a second possible URLLC resource 712, athird possible URLLC resource 714, and a fourth possible URLLC resource716. The second subframe 704 includes a fifth possible URLLC resource718, a sixth possible URLLC resource 720, a seventh possible URLLCresource 722, and an eighth possible URLLC resource 724. The first eMBBDL control information 706 and/or the second eMBB DL control information708 may include one or more indicators used to indicate URLLCcommunication to an eMBB UE.

In some embodiments, the one or more indicators may include multiplebits to represent frequently used sets of subslots for URLLCtransmission. This may more effectively indicate URLLC transmissionsubslots with fewer bits than with bitmap indication. For example, Table1 and Table 2 show the usages of URLLC transmission in one subframe.Each URLLC transmission usage is indicated by 2 bits and 3 bits in thereservation indication field in the eMBB control information in Table 1and Table 2, respectively. In Table 1 and Table 2, it is assumed thatthere are 4 potential transmission subslots in one subframe for URLLCtransmission, so the length of bits in usage field is 4. Each bit in theusage field represents reserved or not reserved (e.g., “1” representsreserved and “0” represents not reserved in the tables).

For example, in Table 1, “01” in the reservation indication field in theeMBB control information corresponds to usage “0101” and is used toindicate that the second and the fourth subslots are not used for eMBBdata transmission in one subframe, meanwhile the first and the thirdsubslots are used for eMBB data transmission, as shown in the firstsubframe 702 of FIG. 7 (e.g., the shaded URLLC possible resources—thesecond possible URLLC resource 712 and the fourth possible URLLCresource 716) and the second subframe 704 of FIG. 7 (e.g., the shadedURLLC possible resources—the sixth possible URLLC resource 720 and theeighth possible URLLC resource 724). The shaded URLLC possible resourcesof the first subframe 702 and the second subframe 704 also work on thecase of “101” in Table 2.

TABLE 1 Value of Reservation Indication Field in eMBB ControlInformation URLLC Usage 00 0000 01 0101 10 1010 11 1111

TABLE 2 Value of Reservation Indication Field in eMBB ControlInformation URLLC Usage 000 0000 001 1000 010 1100 011 1110 100 1010 1010101 110 0111 111 1111

FIG. 8 is a schematic flow chart diagram illustrating one embodiment ofa method 800 for dynamic resource reservation. In some embodiments, themethod 800 is performed by an apparatus, such as the remote unit 102. Incertain embodiments, the method 800 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 800 may include receiving 802 an indication of dynamicresource reservation for ultra-reliable and low latency communication.In certain embodiments, the indication is based on information reportedfrom an ultra-reliable and low latency communication remote unit. Themethod 800 also includes determining 804 a resource based on theindication. In one embodiment, the method 800 includes transmitting 806data on the resource.

In one embodiment, the method 800 includes receiving the indication ofdynamic resource reservation for ultra-reliable and low latencycommunication in enhanced mobile broadband control information. In afurther embodiment, the indication includes a single bit indicatingwhether an ultra-reliable and low latency communication resource patternis used. In certain embodiments, the method 800 includes receivinginformation indicating the ultra-reliable and low latency communicationresource pattern. In some embodiments, the ultra-reliable and lowlatency communication resource pattern is predefined or preconfigured.

In various embodiments, the indication includes multiple bits indicatinga selected ultra-reliable and low latency communication resource patternof multiple ultra-reliable and low latency communication resourcepatterns. In some embodiments, the method 800 includes identifying theselected ultra-reliable and low latency communication resource patternof the multiple ultra-reliable and low latency communication resourcepatterns using the indication.

FIG. 9 is a schematic flow chart diagram illustrating one embodiment ofa method 900 for dynamic resource reservation. In some embodiments, themethod 900 is performed by an apparatus, such as the base unit 104. Incertain embodiments, the method 900 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 900 may include receiving 902 information from anultra-reliable and low latency communication remote unit. In certainembodiments, the information includes a traffic type, a traffic period,a payload size, a delay tolerance, or some combination thereof. Themethod 900 also includes generating 904 an indication of dynamicresource reservation for ultra-reliable and low latency communicationbased on the information. The method 900 includes transmitting 906 theindication of dynamic resource reservation for ultra-reliable and lowlatency communication to an enhanced mobile broadband remote unit.

In one embodiment, the method 900 includes transmitting the indicationof dynamic resource reservation for ultra-reliable and low latencycommunication in enhanced mobile broadband control information. In afurther embodiment, the indication includes a single bit indicatingwhether an ultra-reliable and low latency communication resource patternis used. In certain embodiments, the method 900 includes transmittinginformation indicating the ultra-reliable and low latency communicationresource pattern. In some embodiments, the ultra-reliable and lowlatency communication resource pattern is predefined or preconfigured.In various embodiments, the indication includes multiple bits indicatinga selected ultra-reliable and low latency communication resource patternof multiple ultra-reliable and low latency communication resourcepatterns.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. An apparatus comprising: a receiver that receives an indication ofresource reservation for uplink communication, wherein the indication isbased on information reported from a first remote unit; a processor thatdetermines a resource based on the indication; and a transmitter thattransmits data on the resource.
 2. The apparatus of claim 1, wherein thereceiver receives the indication of resource reservation for uplinkcommunication in downlink control information.
 3. The apparatus of claim1, wherein the indication comprises a single bit indicating whether anuplink communication resource pattern is used.
 4. The apparatus of claim3, wherein the receiver receives information indicating the uplinkcommunication resource pattern.
 5. The apparatus of claim 3, wherein theuplink communication resource pattern is predefined or preconfigured. 6.The apparatus of claim 1, wherein the indication comprises a pluralityof bits indicating a selected uplink communication resource pattern of aplurality of uplink communication resource patterns.
 7. The apparatus ofclaim 6, wherein the processor identifies the selected uplinkcommunication resource pattern of the plurality of uplink communicationresource patterns using the indication.
 8. A method comprising:receiving an indication of resource reservation for uplinkcommunication, wherein the indication is based on information reportedfrom a first remote unit; determining a resource based on theindication; and transmitting data on the resource.
 9. The method ofclaim 8, wherein receiving the indication of resource reservation foruplink communication further comprises receiving the indication ofdynamic resource reservation for uplink communication in downlinkcontrol information.
 10. The method of claim 8, wherein the indicationcomprises a single bit indicating whether an uplink communicationresource pattern is used.
 11. (canceled)
 12. (canceled)
 13. The methodof claim 8, wherein the indication comprises a plurality of bitsindicating a selected uplink communication resource pattern of aplurality of uplink communication resource patterns.
 14. The method ofclaim 13, wherein determining the resource reservation based on theindication further comprises identifying the selected uplinkcommunication resource pattern of the plurality of uplink communicationresource patterns using the indication.
 15. An apparatus comprising: areceiver that receives information from a first remote unit, wherein theinformation comprises a traffic type, a traffic period, a payload size,a delay tolerance, or some combination thereof; a processor thatgenerates an indication of resource reservation for uplink communicationbased on the information; and a transmitter that transmits theindication of resource reservation for uplink communication to a secondremote unit.
 16. The apparatus of claim 15, wherein the transmittertransmits the indication of resource reservation for uplinkcommunication in downlink control information.
 17. The apparatus ofclaim 15, wherein the indication comprises a single bit indicatingwhether an uplink communication resource pattern is used.
 18. Theapparatus of claim 17, wherein the transmitter transmits informationindicating the uplink communication resource pattern.
 19. The apparatusof claim 17, wherein the uplink communication resource pattern ispredefined or preconfigured.
 20. The apparatus of claim 15, wherein theindication comprises a plurality of bits indicating a selected uplinkcommunication resource pattern of a plurality of uplink communicationresource patterns.
 21. A method comprising: receiving information from afirst remote unit, wherein the information comprises a traffic type, atraffic period, a payload size, a delay tolerance, or some combinationthereof; generating an indication of resource reservation for uplinkcommunication based on the information; and transmitting the indicationof resource reservation for uplink communication to a second remoteunit.
 22. (canceled)
 23. (canceled)
 24. (canceled)
 25. (canceled) 26.The method of claim 21, wherein the indication comprises a plurality ofbits indicating a selected uplink communication resource pattern of aplurality of uplink communication resource patterns.